-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌱 Foreground deletion for MachineDeployments and MachineSets #11174
🌱 Foreground deletion for MachineDeployments and MachineSets #11174
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Just for confirming my assumption, cluster deletion won't conflict with foreground deletion because MS an machines which are not directly owned by the cluster are filitered out from cluster descendants that are deleted by the cluster controller
(rif filterOwnedDescendants).
Is that correct?
internal/controllers/machinedeployment/machinedeployment_controller.go
Outdated
Show resolved
Hide resolved
internal/controllers/machinedeployment/machinedeployment_controller.go
Outdated
Show resolved
Hide resolved
internal/controllers/machinedeployment/machinedeployment_controller.go
Outdated
Show resolved
Hide resolved
internal/controllers/machinedeployment/machinedeployment_controller.go
Outdated
Show resolved
Hide resolved
Based on e2e test artifacts - I think yes. But I would say let's run it once through the debugger with Tilt to be sure |
internal/controllers/machinedeployment/machinedeployment_controller.go
Outdated
Show resolved
Hide resolved
internal/controllers/machinedeployment/machinedeployment_controller_test.go
Show resolved
Hide resolved
internal/controllers/machinedeployment/machinedeployment_controller_test.go
Outdated
Show resolved
Hide resolved
internal/controllers/machinedeployment/machinedeployment_controller_test.go
Outdated
Show resolved
Hide resolved
6140c34
to
87d7f4c
Compare
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main Note: still TODO |
/retest |
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main |
/retest machinepool failure |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice, last round of nits
Thank you very much!! /lgtm (hold is already set, up to you) |
LGTM label has been added. Git tree hash: f231a37f639144f52238c2a2f634efc34a1cda66
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini, sbueringer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-cluster-api-e2e-main |
/hold cancel |
cc @vincepri fyi (as you were interested in this) |
What this PR does / why we need it:
Supersedes #10791
This PR implements foreground deletion in the machinedeployment and machineset controllers using a finalizer.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Part of #10710
/area machinedeployment
/area machineset